Systems, Methods, Apparatuses And Computer Program Products For Providing Notification Of Items For Pickup And Delivery

ABSTRACT

An apparatus is provided for providing notification of items for pickup at a location. The apparatus may include at least one memory and a processor(s) configured to automatically send an electronic message to a network device requesting pickup of an item(s) at a location of a user of the apparatus responsive to detecting pressing of a button on an exterior of the apparatus. The processor is also configured to receive an acknowledgement message from the network device denoting (i) confirmation that the network device received the electronic message requesting pickup of the item(s) at the location of the user and (ii) scheduled pickup of the item(s) from the location of the user at an estimated time. The processor is further configured to generate a visible indication regarding the pickup of the item(s) in response to detecting receipt of the acknowledgement message. Corresponding computer program products and methods are also provided.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation application of, and claims priorityto and the benefit of U.S. Application Serial No. U.S. patentapplication Ser. No. 17/867,104 filed Apr. 12, 2022, which is acontinuation of U.S. patent application Ser. No. 15/615,365 filed Jun.6, 2017, the contents of which are hereby incorporated herein in theirentireties by reference.

TECHNOLOGICAL FIELD

An embodiment of the invention relates generally to a system, method,apparatus, and computer program product for notifying a shipping carrierof one or more items for pickup at a location.

BACKGROUND

Presently, to facilitate pickup of parcels from a customer location, acustomer may typically call a service center of a shipping carrier toschedule and arrange for pickup of a parcel(s) or the customer mayphysically visit a service center of the shipping carrier to scheduleand arrange for pickup of a parcel(s) at a customer location.Alternatively, at present, a customer may typically utilize a mobilephone, computer, tablet or the like to connect to a network such as theInternet to access a webpage of the shipping carrier so that thecustomer may input information (e.g., name, address, type of shipment,etc.) into the webpage to request pickup of a parcel(s) at a customerlocation.

These current approaches typically require the customer to performvarious active steps (e.g., calling a service center, visiting a servicecenter, using an electronic device to access a webpage, etc.) for thecustomer to arrange for pickup up a parcel(s), which may be inefficient,time consuming and burdensome to customers.

As such, a need may exist for a more efficient and less cumbersomeapproach to facilitate scheduling of pickup of parcels at a customerlocation.

BRIEF SUMMARY

The present invention provides systems, methods, apparatuses andcomputer program products for providing notification of one or moreitems for pickup at a location. In this regard, a communication device(e.g., an Internet of Things (IoT) communication device) of theexemplary embodiments may detect a selection/pressing of a push button,which may trigger sending of a message/signal, by the communicationdevice, to a network device to arrange for pickup of an item(s) at alocation (e.g., an address, a GPS location, etc.) of a user of thecommunication device. In response, the communication device may receivean acknowledgement from the network device that the pickup of theitem(s) at the location of the user is scheduled.

In some exemplary embodiments, the acknowledgement may be a signal sentto the communication device which may trigger a light of the push buttonto flash/blink denoting to the user of the communication device that thenetwork device scheduled pickup of the item(s) at the location. In someother exemplary embodiments, the acknowledgement may be a message (alsoreferred to herein as an acknowledgement message) received, by thecommunication device, from the network device confirming that thenetwork device scheduled, and arranged resources (e.g., a assigneddriver and delivery vehicle), for pickup of the item(s) at the locationof the user. The acknowledgement message may also specify an estimatedtime for pickup of the item(s) at the location of the user. Furthermore,upon receipt of the acknowledgement message from the network device, adisplay device of the communication device may display the visibleindicia (e.g., confirmation that pickup of the item(s) at the locationis scheduled and an estimated time for the pickup) of theacknowledgement message to the user of the communication device. In oneexample embodiment, the display device may have a small monochromaticorganic light-emitting diode (OLED) display screen. In other exampleembodiments, the display device may include any other suitable displayscreen configured to display the visible indicia.

The network device of the exemplary embodiments may also provide anelectronic message to the display device of the communication device(e.g., an IoT communication device) of the user notifying the user if ascheduled pickup of one or more items, at a location of the user, isdelayed or cancelled.

Moreover, by utilizing a push button (e.g., in response to adepression/selection of the push button) of a communication device(e.g., an IoT communication device) to trigger automatic sending of asignal(s)/message(s) to a network device requesting pickup of one ormore items at a location of a user, the exemplary embodiments mayconserve computing resources and bandwidth of the communication deviceby not requiring other components (e.g., a user interface for input ofdata of the signal(s)/message(s), a display device for viewing of inputdata, etc.) to perform multiple tasks for generating thesignal(s)/message(s).

In one example embodiment, a method for providing notification of one ormore items for pickup at a location is provided. The method may includeautomatically sending a generated electronic message to a network devicerequesting pickup of one or more items at a location of a user of acommunication device in response to detecting pressing of a button on anexterior of the communication device. The method may further includereceiving an electronic acknowledgement message from the network devicedenoting (i) confirmation that the network device received the generatedelectronic message requesting pickup of the one or more items at thelocation of the user and (ii) scheduled pickup of the one or more itemsfrom the location of the user at an estimated time. The method mayfurther include generating a visible indication regarding the pickup ofthe one or more items in response to detecting receipt of the electronicacknowledgement message.

In another example embodiment, an apparatus for providing notificationof one or more items for pickup at a location is provided. The apparatusmay include a processor and a memory including computer program code.The memory and computer program code are configured to, with the atleast one processor, cause the apparatus to at least perform operationsincluding automatically sending a generated electronic message to anetwork device requesting pickup of one or more items at a location of auser of the apparatus in response to detecting pressing of a button onan exterior of the apparatus. The memory and computer program code arealso configured to, with the processor, cause the apparatus to receivean electronic acknowledgement message from the network device denoting(i) confirmation that the network device received the generatedelectronic message requesting pickup of the one or more items at thelocation of the user and (ii) scheduled pickup of the one or more itemsfrom the location of the user at an estimated time. The memory andcomputer program code are also configured to, with the processor, causethe apparatus to generate a visible indication regarding the pickup ofthe one or more items in response to detecting receipt of the electronicacknowledgement message.

In yet another example embodiment, a computer program product forproviding notification of one or more items for pickup at a location isprovided. The computer program product includes at least onecomputer-readable storage medium having computer-executable program codeinstructions stored therein. The computer-executable program codeinstructions may include program code instructions configured toautomatically send a generated electronic message to a network devicerequesting pickup of one or more items at a location of a user of anapparatus in response to detecting pressing of a button on an exteriorof the apparatus. The computer program product may further includeprogram code instructions configured to cause receipt of an electronicacknowledgement message from the network device denoting (i)confirmation that the network device received the generated electronicmessage requesting pickup of the one or more items at the location ofthe user and (ii) scheduled pickup of the one or more items from thelocation of the user at an estimated time. The computer program productmay further include program code instructions configured to generate avisible indication regarding the pickup of the one or more items inresponse to detecting receipt of the electronic acknowledgement message.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Having thus described the invention in general terms, reference will nowbe made to the accompanying drawings, which are not necessarily drawn toscale, and wherein:

FIG. 1 is a diagram of a system that can be used to practice variousembodiments of the present invention.

FIG. 2 is a diagram of an information/data collection device that may beused in association with certain embodiments of the present invention.

FIG. 3 is a schematic of a management computing entity in accordancewith certain embodiments of the present invention.

FIG. 4 is a schematic of a mobile computing entity in accordance withcertain embodiments of the present invention.

FIG. 5 is a diagram of an IoT computing entity that may be used inassociation with certain embodiments of the present invention.

FIG. 6 is a flowchart illustrating operations and processes that can beused in accordance with various embodiments of the present invention.

DETAILED DESCRIPTION

Various embodiments of the present invention now will be described morefully hereinafter with reference to the accompanying drawings, in whichsome, but not all embodiments of the inventions are shown. Indeed, theseinventions may be embodied in many different forms and should not beconstrued as limited to the embodiments set forth herein; rather, theseembodiments are provided so that this disclosure will satisfy applicablelegal requirements. The term “or” is used herein in both the alternativeand conjunctive sense, unless otherwise indicated. The terms“illustrative” and “exemplary” are used to be examples with noindication of quality level. Like numbers refer to like elementsthroughout.

I. Methods, Apparatuses, Systems, and Computer Program Products

Embodiments of the present invention may be implemented in various ways,including as computer program products that comprise articles ofmanufacture. A computer program product may include a non-transitorycomputer-readable storage medium storing applications, programs, programmodules, scripts, source code, program code, object code, byte code,compiled code, interpreted code, machine code, executable instructions,and/or the like (also referred to herein as executable instructions,instructions for execution, program code, and/or similar terms usedherein interchangeably). Such non-transitory computer-readable storagemedia include all computer-readable media (including volatile andnon-volatile media).

In one embodiment, a non-volatile computer-readable storage medium mayinclude a floppy disk, flexible disk, hard disk, solid-state storage(SSS) (e.g., a solid state drive (SSD), solid state card (SSC), solidstate module (SSM)), enterprise flash drive, magnetic tape, or any othernon-transitory magnetic medium, and/or the like. A non-volatilecomputer-readable storage medium may also include a punch card, papertape, optical mark sheet (or any other physical medium with patterns ofholes or other optically recognizable indicia), compact disc read onlymemory (CD-ROM), compact disc-rewritable (CD-RW), digital versatile disc(DVD), Blu-ray disc (BD), any other non-transitory optical medium,and/or the like. Such a non-volatile computer-readable storage mediummay also include read-only memory (ROM), programmable read-only memory(PROM), erasable programmable read-only memory (EPROM), electricallyerasable programmable read-only memory (EEPROM), flash memory (e.g.,Serial, NAND, NOR, and/or the like), multimedia memory cards (MIVIC),secure digital (SD) memory cards, SmartMedia cards, CompactFlash (CF)cards, Memory Sticks, and/or the like. Further, a non-volatilecomputer-readable storage medium may also include conductive-bridgingrandom access memory (CBRAM), phase-change random access memory (PRAM),ferroelectric random-access memory (FeRAM), non-volatile random-accessmemory (NVRAM), magnetoresistive random-access memory (MRAM), resistiverandom-access memory (RRAM), Silicon-Oxide-Nitride-Oxide-Silicon memory(SONOS), floating junction gate random access memory (FJG RAM),Millipede memory, racetrack memory, and/or the like.

In one embodiment, a volatile computer-readable storage medium mayinclude random access memory (RAM), dynamic random access memory (DRAM),static random access memory (SRAM), fast page mode dynamic random accessmemory (FPM DRAM), extended data-out dynamic random access memory (EDODRAM), synchronous dynamic random access memory (SDRAM), doubleinformation/data rate synchronous dynamic random access memory (DDRSDRAM), double information/data rate type two synchronous dynamic randomaccess memory (DDR2 SDRAM), double information/data rate type threesynchronous dynamic random access memory (DDR3 SDRAM), Rambus dynamicrandom access memory (RDRAM), Twin Transistor RAM (TTRAM), Thyristor RAM(T-RAM), Zero-capacitor (Z-RAM), Rambus in-line memory module (RIMM),dual in-line memory module (DIMM), single in-line memory module (SIMM),video random access memory (VRAM), cache memory (including variouslevels), flash memory, register memory, and/or the like. It will beappreciated that where embodiments are described to use acomputer-readable storage medium, other types of computer-readablestorage media may be substituted for or used in addition to thecomputer-readable storage media described above.

As should be appreciated, various embodiments of the present inventionmay also be implemented as methods, apparatus, systems, computingdevices, computing entities, and/or the like. As such, embodiments ofthe present invention may take the form of an apparatus, system,computing device, computing entity, and/or the like executinginstructions stored on a computer-readable storage medium to performcertain steps or operations. However, embodiments of the presentinvention may also take the form of an entirely hardware embodimentperforming certain steps or operations.

Embodiments of the present invention are described below with referenceto block diagrams and flowchart illustrations. Thus, it should beunderstood that each block of the block diagrams and flowchartillustrations may be implemented in the form of a computer programproduct, an entirely hardware embodiment, a combination of hardware andcomputer program products, and/or apparatus, systems, computing devices,computing entities, and/or the like carrying out instructions,operations, steps, and similar words used interchangeably (e.g., theexecutable instructions, instructions for execution, program code,and/or the like) on a computer-readable storage medium for execution.For example, retrieval, loading, and execution of code may be performedsequentially such that one instruction is retrieved, loaded, andexecuted at a time. In some exemplary embodiments, retrieval, loading,and/or execution may be performed in parallel such that multipleinstructions are retrieved, loaded, and/or executed together. Thus, suchembodiments can produce specifically-configured machines performing thesteps or operations specified in the block diagrams and flowchartillustrations. Accordingly, the block diagrams and flowchartillustrations support various combinations of embodiments for performingthe specified instructions, operations, or steps.

II. Exemplary System Architecture

FIG. 1 provides an illustration of a system that can be used inconjunction with various embodiments of the present invention. As shownin FIG. 1 , the system may include one or more vehicles (e.g., deliveryvehicles 100) one or more Internet of Things (IoT) computing entities130, one or more mobile computing entities 105, one or more managementcomputing entities 110, one or more user computing entities 117, one ormore Global Positioning System (GPS) satellites 115, one or morelocation sensors 120, one or more information/data collection devices130, one or more telematics sensors 125, one or more networks 135,and/or the like. Each of the components of the system may be inelectronic communication with, for example, one another over the same ordifferent wireless or wired networks including, for example, a wirelesscellular network, a wired or wireless Personal Area Network (PAN), LocalArea Network (LAN), Metropolitan Area Network (MAN), Wide Area Network(WAN), or the like. Additionally, while FIG. 1 illustrates certainsystem entities as separate, standalone entities, the variousembodiments are not limited to this particular architecture.

1. Exemplary Delivery Vehicle

As discussed herein, a delivery vehicle 100 may be a human operabledelivery vehicle configured for transporting a vehicle operator and aplurality of items along a delivery route. For example, a vehicle 100may be a manned or an unmanned tractor, truck, car, motorcycle, moped,Segway, bicycle, golf cart, hand truck, cart, trailer, tractor andtrailer combination, van, flatbed truck, vehicle, drone, airplane,helicopter, boat, barge, and/or any other form of object for moving ortransporting people, UAVs, and/or shipments/items (e.g., one or morepackages, parcels, bags, containers, loads, crates, items bandedtogether, vehicle parts, pallets, drums, the like, and/or similar wordsused herein interchangeably). In one embodiment, each vehicle 100 may beassociated with a unique vehicle identifier (such as a vehicle ID) thatuniquely identifies the vehicle 100. The unique vehicle ID (e.g.,trailer ID, tractor ID, vehicle ID, and/or the like) may includecharacters, such as numbers, letters, symbols, and/or the like. Forexample, an alphanumeric vehicle ID (e.g., “AS445”) may be associatedwith each vehicle 100. In another embodiment, the unique vehicle ID maybe the license plate, registration number, or other identifyinginformation/data assigned to the vehicle 100. In various embodiments,the delivery vehicle 100 may be configured as discussed in co-pendingU.S. patent application Ser. No. 15/582,129, filed Apr. 28, 2017, andincorporated herein by reference in its entirety. Moreover, although notshown, the interior of the delivery vehicle 100 may comprise a cargoarea configured for storing a plurality of items and/or the like.

Furthermore, the delivery vehicle 100 may comprise and/or be associatedwith one or more computing entities, devices, and/or similar words usedherein interchangeably. For example, the delivery vehicle 100 may beassociated with an information/data collection device 132 or othercomputing entities. In general, the terms computing entity, entity,device, system, and/or similar words used herein interchangeably mayrefer to, for example, one or more computers, computing entities,desktop computers, mobile phones, tablets, phablets, notebooks, laptops,distributed systems, gaming consoles (e.g., Xbox, Play Station, Wii),watches, glasses, iBeacons, proximity beacons, key fobs, RFID tags, earpieces, scanners, televisions, dongles, cameras, wristbands, wearableitems/devices, items/devices, vehicles, kiosks, input terminals, serversor server networks, blades, gateways, switches, processing devices,processing entities, set-top boxes, relays, routers, network accesspoints, base stations, the like, and/or any combination of devices orentities adapted to perform the functions, operations, and/or processesdescribed herein.

FIG. 2 provides a block diagram of an exemplary information/datacollection device 132 that may be attached, affixed, disposed upon,integrated into, or part of a vehicle 100. The information/datacollection device 132 may collect telematics information/data (includinglocation data) and transmit/send the information/data to the mobilecomputing entity 105, the management computing entity 110, and/orvarious other computing entities via one of several communicationmethods.

In one embodiment, the information/data collection device 132 mayinclude, be associated with, or be in wired or wireless communicationwith one or more processors 300 (various exemplary processors aredescribed in greater detail below), one or more location-determiningdevices or one or more location sensors 120 (e.g., Global NavigationSatellite System (GNSS) sensors), one or more telematics sensors 125,one or more real-time clocks 315, a J-Bus protocol architecture, one ormore electronic control modules (ECM) 345, one or more communicationports 330 for receiving telematics information/data from various sensors(e.g., via a CAN-bus), one or more communication ports 305 fortransmitting/sending data, one or more RFID tags/sensors 350, one ormore power sources 320, one or more information/data radios 335 forcommunication with a variety of communication networks, one or morememory modules 310, and one or more programmable logic controllers (PLC)325. It should be noted that many of these components may be located inthe vehicle 100 but external to the information/data collection device132.

In one embodiment, the one or more location sensors 120, modules, orsimilar words used herein interchangeably may be one of severalcomponents in wired or wireless communication with or available to theinformation/data collection device 132. Moreover, the one or morelocation sensors 120 may be compatible with GPS satellites 115, such asLow Earth Orbit (LEO) satellite systems, Department of Defense (DOD)satellite systems, the European Union Galileo positioning systems, theChinese Compass navigation systems, Indian Regional Navigationalsatellite systems, and/or the like. This information/data can becollected using a variety of coordinate systems, such as the DecimalDegrees (DD); Degrees, Minutes, Seconds (DMS); Universal TransverseMercator (UTM); Universal Polar Stereographic (UPS) coordinate systems;and/or the like. Alternatively, triangulation may be used in connectionwith a device associated with a particular vehicle and/or the vehicle'soperator and with various communication points (e.g., cellular towers orWi-Fi access points) positioned at various locations throughout ageographic area to monitor the location of the vehicle 100 and/or itsoperator. The one or more location sensors 120 may be used to receivelatitude, longitude, altitude, heading or direction, geocode, course,position, time, and/or speed information/data (e.g., referred to hereinas telematics information/data and further described herein below). Theone or more location sensors 120 may also communicate with themanagement computing entity 110, the information/data collection device132, mobile computing entity 105, the user computing entity 117 and/orsimilar computing entities.

As indicated, in addition to the one or more location sensors 120, theinformation/data collection device 132 may include and/or be associatedwith one or more telematics sensors 125, modules, and/or similar wordsused herein interchangeably. For example, the telematics sensors 125 mayinclude vehicle sensors, such as engine, fuel, odometer, hubometer, tirepressure, location, weight, emissions, door, and speed sensors. Thetelematics information/data may include, but is not limited to, speeddata, emissions data, RPM data, tire pressure data, oil pressure data,seat belt usage data, distance data, fuel data, idle data, and/or thelike (e.g., referred to herein as telematics data). The telematicssensors 125 may include environmental sensors, such as air qualitysensors, temperature sensors, and/or the like. Thus, the telematicsinformation/data may also include carbon monoxide (CO), nitrogen oxides(NOx), sulfur oxides (SOx), Ethylene Oxide (EtO), ozone (03), hydrogensulfide (H2S) and/or ammonium (NH4) data, and/or meteorologicalinformation/data (e.g., referred to herein as telematics data).

In one embodiment, the ECM 345 may be one of several components incommunication with and/or available to the information/data collectiondevice 132. The ECM 345, which may be a scalable and subservient deviceto the information/data collection device 132, may have information/dataprocessing capability to decode and store analog and digital inputs fromvehicle systems and sensors. The ECM 345 may further haveinformation/data processing capability to collect and present telematicsinformation/data to the J-Bus (which may allow transmission to theinformation/data collection device 132), and output standard vehiclediagnostic codes when received from a vehicle's J-Bus-compatibleon-board controllers 340 and/or sensors.

As indicated, a communication port 330 may be one of several componentsavailable in the information/data collection device 132 (or be in or asa separate computing entity). Embodiments of the communication port 330may include an Infrared information/data Association (IrDA)communication port, an information/data radio, and/or a serial port. Thecommunication port 330 may receive instructions for the information/datacollection device 132. These instructions may be specific to the vehicle100 in which the information/data collection device 132 is installed,specific to the geographic area in which the vehicle 100 will betraveling, specific to the function the vehicle 100 serves within afleet, and/or the like. In one embodiment, the information/data radio335 may be configured to communicate with a wireless wide area network(WWAN), wireless local area network (WLAN), wireless personal areanetwork (WPAN), or any combination thereof. For example, theinformation/data radio 335 may communicate via various wirelessprotocols, such as 802.11, general packet radio service (GPRS),Universal Mobile Telecommunications System (UMTS), Code DivisionMultiple Access 2000 (CDMA2000), CDMA2000 1× (1×RTT), Wideband CodeDivision Multiple Access (WCDMA), Time Division-Synchronous CodeDivision Multiple Access (TD-SCDMA), Long Term Evolution (LTE), EvolvedUniversal Terrestrial Radio Access Network (E-UTRAN), Evolution-DataOptimized (EVDO), High Speed Packet Access (HSPA), High-Speed DownlinkPacket Access (HSDPA), IEEE 802.11 (Wi-Fi), 802.16 (WiMAX),ultra-wideband (UWB), infrared (IR) protocols, Bluetooth protocols(including Bluetooth low energy (BLE)), wireless universal serial bus(USB) protocols, and/or any other wireless protocol.

2. Exemplary Management Computing Entity

FIG. 3 provides a schematic of a management computing entity 110according to one embodiment of the present invention. The managementcomputing entity can be operated by a variety of entities, including acarrier. A carrier may be a traditional carrier, such as United ParcelService (UPS), FedEx, DHL, courier services, the United States PostalService (USPS), Canadian Post, freight companies (e.g. truck-load,less-than-truckload, rail carriers, air carriers, ocean carriers, etc.),and/or the like. However, a carrier may also be a nontraditionalcarrier, such as Coyote, Amazon, Google, Uber, ride-sharing services,crowd-sourcing services, retailers, and/or the like.

In general, the terms computing entity, entity, device, system and/orsimilar words used herein interchangeably may refer to, for example, oneor more computers, computing entities, computing devices, mobile phones,gaming consoles (e.g., Xbox, Play Station, Wii), desktops, tablets,notebooks, laptops, distributed systems, servers or server networks,blades, gateways, switches, processing devices, processing entities,set-top boxes, relays, routers, network access points, base stations,the like, and/or any combination of devices or entities adapted toperform the functions, operations, and/or processes described herein.However, the management computing entity 110 may also comprise variousother systems, such as an Address Matching System (AMS), an InternetMembership System (IMS), a Customer Profile System (CPS), a PackageCenter Information System (PCIS), a Customized Pickup and DeliverySystem (CPAD), a Web Content Management System (WCMS), a NotificationEmail System (NES), a Fraud Prevention System (FPS), and a variety ofother systems and their corresponding components. The managementcomputing entity 110 may also be in communication with various paymentnetworks/systems for carrying out or facilitating the payment of fees.As will be recognized, the payment of such fees may be in a variety offorms, such as via debit cards, credit cards, direct credits, directdebits, cash, check, money order, Internet banking, e-commerce paymentnetworks/systems (e.g., PayPal™ Google Wallet, Amazon Payments), virtualcurrencies (e.g., Bitcoins), award or reward points, and/or the like.

As will be understood from FIG. 3 , in one embodiment, the managementcomputing entity 110 includes one or more processors 205 thatcommunicate with other elements within the management computing entity110 via a system interface or bus 261. The processor 205 may be embodiedin a number of different ways. For example, the processor 205 may beembodied as a processing element, processing circuitry, a coprocessor, acontroller or various other processing devices including integratedcircuits such as, for example, an application specific integratedcircuit (ASIC), a field programmable gate array (FPGA), a hardwareaccelerator, or the like.

In an exemplary embodiment, the processor 205 may be configured toexecute instructions stored in memory or otherwise accessible to theprocessor 205. As such, whether configured by hardware or softwaremethods, or by a combination thereof, the processor 205 may represent anentity capable of performing operations according to embodiments of thepresent invention when configured accordingly. A display device/inputdevice 264 for receiving and displaying data may also be included in themanagement computing entity 110. This display device/input device 264may be, for example, a keyboard or pointing device that is used incombination with a monitor. The management computing entity 110 mayfurther include transitory and non-transitory memory 263, which mayinclude both random access memory (RAM) 267 and read only memory (ROM)265. The ROM 265 of the management computing entity 110 may be used tostore a basic input/output system (BIOS) 226 containing the basicroutines that help to transfer information to the different elementswithin the management computing entity 110.

In addition, in one embodiment, the management computing entity 110 mayinclude at least one storage device 268, such as a hard disk drive, a CDdrive, and/or an optical disk drive for storing information on variouscomputer-readable media. The storage device(s) 268 and its associatedcomputer-readable media may provide nonvolatile storage. Thecomputer-readable media described above could be replaced by any othertype of computer-readable media, such as embedded or removablemultimedia memory cards (M1VICs), secure digital (SD) memory cards,Memory Sticks, electrically erasable programmable read-only memory(EEPROM), flash memory, hard disk, or the like. Additionally, each ofthese storage devices 268 may be connected to the system bus 261 by anappropriate interface.

Furthermore, a number of executable instructions, applications, programmodules, and/or the like may be stored by the various storage devices268 and/or within RAM 267. Such executable instructions, applications,program modules, and/or the like may include an operating system 280, aregistration module 270, a message module 260, a dispatch module 250, anidentification module 245, and/or the like. As discussed in more detailbelow, these executable instructions, applications, program modules,and/or the like may control certain aspects of the operation of themanagement computing entity 110 with the assistance of the processor 205and operating system 280—although their functionality need not bemodularized. In addition to the program modules, the managementcomputing entity 110 may store or be in communication with one or moredatabases, such as database 240.

In an exemplary embodiment, the processor 205 may be in communicationwith and may otherwise control the dispatch module 250. The dispatchmodule 250 may operate in accordance with software embodied in memory(e.g., memory 263, storage device 268) to perform the correspondingfunctions of the dispatch module 250, as described below. In examples inwhich software is employed, a device or circuitry (e.g., processor 205in one example) executing the software forms the structure associatedwith such means. As such, for example, in some example embodiments, thedispatch module 250 may be configured to, among other things, facilitategeneration of one or more messages (e.g., an acknowledgement message)confirming receipt of a request for pickup of one or more items at alocation of a user and arranging/scheduling (e.g., scheduling anestimated time for pickup, assigning a dispatch driver and a deliveryvehicle, etc.) for pickup of the items at the location and for deliveryof the items to a destination address, as described more fully below.

Also located within the management computing entity 110, in oneembodiment, is a network interface 274 for interfacing with variouscomputing entities (e.g., with one or more mobile computing entities105, IoT computing entities 130, user computing entities 117). Forexample, the management computing entity 110 may be able to receive dataand/or messages from and transmit data and/or messages to the mobilecomputing entity 105, IoT computing entity 130, and user computingentity 117. This communication may be via the same or different wired orwireless networks (or a combination of wired and wireless networks). Forinstance, the communication may be executed using a wired datatransmission protocol, such as fiber distributed data interface (FDDI),digital subscriber line (DSL), Ethernet, asynchronous transfer mode(ATM), frame relay, data over cable service interface specification(DOCSIS), or any other wired transmission protocol. Similarly, themanagement computing entity 110 may be configured to communicate viawireless external communication networks using any of a variety ofprotocols, such as 802.11, general packet radio service (GPRS),Universal Mobile Telecommunications System (UMTS), Code DivisionMultiple Access 2000 (CDMA2000), CDMA2000 1× (1×RTT), Wideband CodeDivision Multiple Access (WCDMA), Time Division-Synchronous CodeDivision Multiple Access (TD-SCDMA), Long Term Evolution (LTE), EvolvedUniversal Terrestrial Radio Access Network (E-UTRAN), Evolution-DataOptimized (EVDO), High Speed Packet Access (HSPA), High-Speed DownlinkPacket Access (HSDPA), IEEE 802.11 (Wi-Fi), 802.16 (WiMAX),ultra-wideband (UWB), infrared (IR) protocols, Bluetooth™ protocols,wireless universal serial bus (USB) protocols, and/or any other wirelessprotocol.

It will be appreciated that one or more of the components of themanagement computing entity 110 may be located remotely from othermanagement computing entity 110 components. Furthermore, one or more ofthe components may be combined and additional components performingfunctions described herein may be included in the management computingentity 110.

3. Exemplary Mobile Computing Entity

FIG. 4 provides an illustrative schematic representative of a mobilecomputing entity 105 that can be used in conjunction with embodiments ofthe present invention. In one embodiment, a mobile computing entity(e.g., a Delivery Information Acquisition Device (DIAD)) may be carriedfor use by carrier personnel. In one embodiment, the mobile computingentities 105 may include one or more components that are functionallysimilar to those of the management computing entity 110 and/or asdescribed below. As will be recognized, mobile computing entities 105can be operated by various parties, including personnel collecting,delivering, transporting items, maintenance personnel, and dispatchers.As shown in FIG. 4 , a mobile computing entity 105 can include anantenna 412, a transmitter 404 (e.g., radio), a receiver 406 (e.g.,radio), and a processing element 408 that provides signals to andreceives signals from the transmitter 404 and receiver 406,respectively.

The signals provided to and received from the transmitter 404 and thereceiver 406, respectively, may include signaling information/data inaccordance with an air interface standard of applicable wireless systemsto communicate with various entities, such as IoT computing entities130, management computing entities 110, and/or the like. In this regard,the mobile computing entity 105 may be capable of operating with one ormore air interface standards, communication protocols, modulation types,and access types. More particularly, the mobile computing entity 105 mayoperate in accordance with any of a number of wireless communicationstandards and protocols. In a particular embodiment, the mobilecomputing entity 105 may operate in accordance with multiple wirelesscommunication standards and protocols, such as GPRS, UMTS, CDMA2000,1×RTT, WCDMA, TD-SCDMA, LTE, E-UTRAN, EVDO, HSPA, HSDPA, Wi-Fi, WiMAX,UWB, IR protocols, Bluetooth protocols, USB protocols, and/or any otherwireless protocol.

Via these communication standards and protocols, the mobile computingentity 105 can communicate with various other entities using conceptssuch as Unstructured Supplementary Service information/data (US SD),Short Message Service (SMS), Multimedia Messaging Service (MMS),Dual-Tone Multi-Frequency Signaling (DTMF), and/or Subscriber IdentityModule Dialer (SIM dialer). The mobile computing entity 105 can alsodownload changes, add-ons, and updates, for instance, to its firmware,software (e.g., including executable instructions, applications, programmodules), and operating system.

According to one embodiment, the mobile computing entity 105 may includelocation determining aspects, devices, modules, functionalities, and/orsimilar words used herein interchangeably. For example, the mobilecomputing entity 105 may include outdoor positioning aspects, such as alocation module adapted to acquire, for example, latitude, longitude,altitude, geocode, course, direction, heading, speed, UTC, date, and/orvarious other information/data. In one embodiment, the location modulecan acquire data, sometimes known as ephemeris data, by identifying thenumber of satellites in view and the relative positions of thosesatellites. The satellites may be a variety of different satellites,including LEO satellite systems, DOD satellite systems, the EuropeanUnion Galileo positioning systems, GLONASS, the Chinese Compassnavigation systems, Indian Regional Navigational satellite systems,and/or the like. Additionally, the location module may be compatiblewith A-GPS (Assisted GPS) for quick time to first fix and jump startingthe ability of the location module to acquire location almanac andephemeris data, and/or be compatible with SBAS such as WAAS, EGNOS,MSAS, and/or GAGN to increase GPS accuracy. Alternatively, the locationinformation/data may be determined by triangulating the mobile computingentity's 105 position in connection with a variety of other systems,including cellular towers, Wi-Fi access points, and/or the like.Similarly, the mobile computing entity 105 may include indoorpositioning aspects, such as a location module adapted to acquire, forexample, latitude, longitude, altitude, geocode, course, direction,heading, speed, time, date, and/or various other information/data. Someof the indoor aspects may use various position or location technologiesincluding RFID tags, indoor beacons or transmitters, Wi-Fi accesspoints, cellular towers, nearby computing devices (e.g., smartphones,laptops) and/or the like. For instance, such technologies may includeiBeacons, Gimbal proximity beacons, BLE receivers and/or transmitters,NFC receivers and/or transmitters, and/or the like. These indoorpositioning aspects can be used in a variety of settings to determinethe location of someone or something to within inches or centimeters.

The mobile computing entity 105 may also comprise a user interface (thatcan include a display 416 coupled to a processing element 408) and/or auser input interface (coupled to a processing element 408). For example,the user interface may be an application, browser, user interface,dashboard, webpage, and/or similar words used herein interchangeablyexecuting on and/or accessible via the mobile computing entity 105 tointeract with and/or cause display of information. The user inputinterface can comprise any of a number of devices allowing the mobilecomputing entity 105 to receive data, such as a keypad 418 (hard orsoft), a touch display, voice/speech or motion interfaces, scanners,readers, or other input device. In embodiments including a keypad 418,the keypad 418 can include (or cause display of) the conventionalnumeric (0-9) and related keys (#, *), and other keys used for operatingthe mobile computing entity 105 and may include a full set of alphabetickeys or set of keys that may be activated to provide a full set ofalphanumeric keys. In addition to providing input, the user inputinterface can be used, for example, to activate or deactivate certainfunctions, such as screen savers and/or sleep modes. Through such inputsthe mobile computing entity can collect contextual information/data aspart of the management data.

The mobile computing entity 105 can also include volatile storage ormemory 422 and/or non-volatile storage or memory 424, which can beembedded and/or may be removable. For example, the non-volatile memorymay be ROM, PROM, EPROM, EEPROM, flash memory, MMCs, SD memory cards,Memory Sticks, CBRAM, PRAM, FeRAM, RRAM, SONOS, racetrack memory, and/orthe like. The volatile memory may be RAM, DRAM, SRAM, FPM DRAM, EDODRAM, SDRAM, DDR SDRAM, DDR2 SDRAM, DDR3 SDRAM, RDRAM, RIMM, DIMM, SIMM,VRAM, cache memory, register memory, and/or the like. The volatile andnon-volatile storage or memory can store databases, database instances,database management system entities, data, applications, programs,program modules, scripts, source code, object code, byte code, compiledcode, interpreted code, machine code, executable instructions, and/orthe like to implement the functions of the mobile computing entity 105.

4. IoT Computing Entity

FIG. 5 shows an exemplary embodiment of an IoT computing entity 130. Inone embodiment, the IoT computing entity 130 may include, be associatedwith, or be in wireless communication, or wired, with one or moreprocessors 200 (various exemplary processors are described in greaterdetail below), one or more push buttons 215 (also referred to herein asbutton 215), one or more communication interfaces 230 forreceiving/transmitting information/data from/to various sources (e.g.,management computing entities 110, mobile computing entities 105, etc.),one or more power sources 220, one or more information/data radios 235(also referred to herein as radio device 235) for communication with avariety of communication networks, and one or more memory devices 210.In some example embodiments, the IoT computing entity 130 may alsooptionally include a display device 295. The display device 295 may be alight-emitting diode (LED) display, an organic light-emitting diode(OLED) display or any other suitable display.

Each IoT computing entity 130 may be powered by one or more powersources 220. The power source may be a source provided by a poweroutlet, an energy storage device (e.g., a battery (e.g., a LiFePO4battery, etc.), a supercapacitor, and/or the like), a Universal SerialBus (USB) power charger and/or the like.

In one example embodiment, each IoT computing entity 130 may communicatewith communication devices such as, for example, management computingentities 110, mobile computing entities 105, user computing entities117, printer 297 and the like using a wireless communication standardsuch as, for example Wi-Fi, cellular, Long Range (LoRa) or the like. Insome other exemplary embodiments, each IoT computing entity 130 maycommunicate with communication devices (e.g., management computingentity 110, mobile computing entity 105, user computing entities 117,printer 297, etc.) using wireless communication standards and protocols,including Bluetooth, Wibree, NFC, Wi-Fi, ZigBee, general packet radioservice (GPRS), and/or any other wireless protocol or standard. The IoTcomputing entity 130 may also be in direct or indirect communicationwith the management computing entity 110, the mobile computing entity105, and/or similar computing entities over the same or different wiredor wireless networks.

In another embodiment, an IoT computing entity 130 may be operated inone or more operating modes, such as a monitoring mode, a sleep mode,and/or the like. In the monitoring mode, the IoT computing entity 130may be in a full power mode or a power mode greater than a low powermode (e.g., a sleep mode) and may actively monitor for communications(e.g., receipt of communications from other computing entities (e.g.,management computing entity 110, mobile computing entity 105, etc.) andmay execute instructions. The IoT computing entity 130 may also transmita signal(s) during the monitoring mode. Furthermore, the IoT computingentity 130 may operate in the monitoring mode for a predetermined timeperiod prior to entering a sleep mode.

For example, in an instance in which there are not any communicationstransmitted to or received by the IoT computing entity 130 during thepredetermined time period of the monitoring mode, the IoT computingentity 130 may enter a sleep mode upon expiration of the predeterminedtime period. In sleep mode, the IoT computing entity 130 may removepower to unneeded subsystems and may place other subsystems (e.g., aprocessor (e.g., processor 200), a display (e.g., display device 295),etc.) into a configurable low power state (e.g., with just sufficientpower for the IoT computing entity 130 to detect triggers/events for theIoT computing entity 130 to change/switch from sleep mode into otheroperational modes (e.g., monitoring mode)). The change of theoperational mode may be triggered by various configurabletriggers/events, such as, for example, detection of a selection/pressingof a button (e.g., button 215) which may cause transmission of asignal/message, as well as a message/signal received from a managementcomputing entity 110, a mobile computing entity 105, a user computingentity 117 and/or other appropriate computing entities, combinationsthereof, and/or the like. By utilizing the sleep mode, the IoT computingentity 130 may be able to conserve energy and reduce consumption of abattery of a power source (e.g., power source 220).

As indicated, a communication interface(s) 230 may be one of severalcomponents available in the IoT computing entity 130. Embodiments of thecommunication interface(s) 230 may include an Infrared information/dataAssociation (IrDA) communication port, an information/data radio, and/ora serial port. In an exemplary embodiment, the communicationinterface(s) 230 may receive instructions for the IoT computing entity130. In one exemplary embodiment, the IoT computing entity 130 maycommunicate using a Message Queue Telemetry Transport (MATT) protocol orany other suitable protocol. Further, in one exemplary embodiment, theinformation/data radio 235 may be configured to communicate with anetwork via Wi-Fi (e.g., IEEE 802.11), Wi-Fi Direct and/or the like. Insome other exemplary embodiments, the information/data radio 235 may beconfigured to communicate with wireless wide area network (WWAN),wireless local area network (WLAN), wireless personal area network(WPAN), or any combination thereof. For example, the information/dataradio 235 may communicate via various wireless protocols, such as802.11, general packet radio service (GPRS), Universal MobileTelecommunications System (UMTS), Code Division Multiple Access 2000(CDMA2000), CDMA2000 1× (1×RTT), Wideband Code Division Multiple Access(WCDMA), Global System for Mobile Communications (GSM), Enhanced Datarates for GSM Evolution (EDGE), Time Division-Synchronous Code DivisionMultiple Access (TD-SCDMA), Long Term Evolution (LTE), Evolved UniversalTerrestrial Radio Access Network (E-UTRAN), Evolution-Data Optimized(EVDO), High Speed Packet Access (HSPA), High-Speed Downlink PacketAccess (HSDPA), IEEE 802.11 (Wi-Fi), Wi-Fi Direct, 802.16 (WiMAX),ultra-wideband (UWB), infrared (IR) protocols, near field communication(NFC) protocols, Wibree, Bluetooth protocols (including Bluetooth LowEnergy (BLE)), wireless universal serial bus (USB) protocols, and/or anyother wireless protocol such as, for example, LoRa.

According to one embodiment, the IoT computing entity 130 may includelocation determining aspects, devices, modules, functionalities, and/orsimilar words used herein interchangeably. For example, the IoTcomputing entity 130 may include outdoor positioning aspects, such as alocation module 290 adapted to acquire, for example, latitude,longitude, altitude, geocode, course, direction, heading, speed, UTC,date, and/or various other information/data. In one embodiment, thelocation module 290 may acquire data, sometimes known as ephemeris data,by identifying the number of satellites in view and the relativepositions of those satellites. The satellites may be a variety ofdifferent satellites, including LEO satellite systems, DOD satellitesystems, the European Union Galileo positioning systems, GLONASS, theChinese Compass navigation systems, Indian Regional Navigationalsatellite systems, and/or the like. Additionally, the location module290 may be compatible with A-GPS for quick time to first fix and jumpstarting the ability of the location module 290 to acquire locationalmanac and ephemeris data, and/or be compatible with SBAS such as WAAS,EGNOS, MSAS, and/or GAGN to increase GPS accuracy. Alternatively, thelocation information/data may be determined by triangulating theposition of the IoT computing entity 130 in connection with a variety ofother systems, including cellular towers, Wi-Fi access points, and/orthe like. Similarly, the IoT computing entity 130 may include indoorpositioning aspects, such as a location module 290 adapted to acquire,for example, latitude, longitude, altitude, geocode, course, direction,heading, speed, time, date, and/or various other information/data. Someof the indoor aspects may use various position or location technologiesincluding RFID tags, indoor beacons or transmitters, Wi-Fi accesspoints, cellular towers, nearby computing devices (e.g., smartphones,laptops) and/or the like. For example, such technologies may includeiBeacons, Gimbal proximity beacons, BLE receivers and/or transmitters,NFC receivers and/or transmitters, and/or the like. These indoorpositioning aspects can be used in a variety of settings to determinethe location of someone or something to within inches or centimeters.

As described more fully below, the IoT computing entity 130 may detect aselection/pressing of a push button 215, which may trigger sending of amessage/signal, by the IoT computing entity 130, to the managementcomputing entity 110 to arrange for pickup of an item(s) at a location(e.g., an address, a GPS location, etc.) of a user of the IoT computingentity 130. In response, the IoT computing entity 130 may receive anelectronic acknowledgement from the management computing entity 110 thatthe pickup of the item(s) at the location of the user is scheduled.

In one exemplary embodiment, the acknowledgement may be a signal sent tothe IoT computing entity 130 which causes a light of the push button 215to flash/blink denoting to the user of the IoT computing entity 130 thatthe management computing entity 110 scheduled pickup of the item(s) atthe location. In another exemplary embodiment, the acknowledgement maybe a message received, by the IoT computing entity 130, from themanagement computing entity 110 confirming that the management computingentity 110 scheduled, and arranged resources (e.g., a dispatch driverand a vehicle), for pickup of the item(s) at the location of the user.The message may also specify an estimated time for pickup of the item(s)at the location of the user. Furthermore, upon receipt of the messagefrom the management computing entity 110, the display device 295 of theIoT computing entity 130 may display (e.g., via an OLED display of thedisplay device 295) the visible indicia (e.g., confirmation that pickupof the item(s) at the location is scheduled and an estimated time forpickup) of the message to the user of the IoT computing entity 130.

5. Exemplary User Computing Entity

In one embodiment, the user computing entities 117 may each include oneor more components that are functionally similar to those of themanagement computing entity 110 and/or the mobile computing entity 105.For example, in one embodiment, each of the user computing entities 117may include: (1) a processing element that communicates with otherelements via a system interface or bus; (2) a user interface; (3)transitory and non-transitory memory; and (4) a communicationsinterface. As previously noted, the computing entities 117 may comprisea user interface. For example, the user interface may be an application,browser, user interface, dashboard, webpage, and/or similar words usedherein interchangeably executing on and/or accessible via the usercomputing entities 117 to interact with and/or cause display ofinformation/data from the management computing entity 110, the mobilecomputing entity 105, and/or another appropriate computing entity, asdescribed herein. The user input interface can comprise any of a numberof devices allowing the user computing entities 117 to receive data,such as a keypad (hard or soft), a touch display, voice/speech or motioninterfaces, scanners, readers, or other input device. In addition toproviding input, the user input interface can be used, for example, toactivate or deactivate certain functions, such as screen savers and/orsleep modes. These architectures are provided for exemplary purposesonly and are not limiting to the various embodiments.

6. Exemplary Items

In one embodiment, an item(s) may be any tangible and/or physicalobject. In another embodiment, an item may be enclosed in one or morepackages, envelopes, parcels, bags, goods, products, loads, crates,items banded together, drums, the like, and/or similar words used hereininterchangeably.

III. Exemplary System Operation

Reference will now be made to exemplary embodiments of a system thatautomatically arranges (e.g., schedules) for pickup of an item(s) at alocation of a user in response to receipt of a signal/message from anIoT computing device in an instance in which a push button of the IoTcomputing device is selected/depressed, as described more fully below.

Operation of Exemplary Embodiments

In one exemplary embodiment, a user of an IoT computing device 110 mayutilize a user computing entity 117 to communicate with the registrationmodule 270 of the management computing entity 110 in order to setup/register a profile with the management computing entity 110, whichmay be maintained by a shipping carrier. In some other exemplaryembodiments, a private blockchain (e.g., a server, a distributeddatabase server) may also be utilized to set up/register a profile(e.g., a user profile) with the management computing entity 110 and mayauthorize and authenticate the user. The registration module 270 of themanagement computing entity 110 may provide a webpage to the usercomputing entity 117 so that the user may utilize a user interface ofthe user computing entity 117 to register the profile with themanagement computing entity. The profile may include data associatedwith authentication credentials (e.g., username, password, etc.) andaccount information (e.g., customer account information (e.g., a creditcard account, etc.)) of the user to cover costs associated withshipments of one or more items. The profile may also include one or morelocations such as, for example, one or more addressees of the user atwhich to pickup one or more items for delivery by the shipping carrierand may indicate a destination address at which to deliver one or moreitems. The management computing entity 110 may store the profile inmemory 263 or storage device 268.

In one exemplary embodiment, a user of an IoT computing entity 130desiring to have one or more items picked up for delivery from alocation of the user may press/select the button 215 on the IoTcomputing entity 130. In this regard, the processor 200 of the IoTcomputing entity 130 may detect the pressing/selecting of the button215, which may automatically trigger the processor 200 to generate andsend a signal(s) or message(s) to the management computing entity 110(e.g., to the dispatch module 250 of the management computing entity110) requesting pickup of one or more items at a location (e.g., anaddress location, a geolocation (e.g., a GPS location)) of the user. Insome exemplary embodiments, the signal(s)/message(s) generated by theprocessor 200 of the IoT computing device 130 may include dataindicating a geolocation (e.g., latitude and longitude coordinates) ofthe IoT computing entity 130. The geolocation of the IoT computingentity 130 may be determined by the location module 290 and may beprovided to the processor 200 for inclusion in the signal(s)/message(s).

In response to the processor 205 of the management computing entity 130receiving the signal(s) or message(s) from the IoT computing entity 130,the processor 205 of the management computing entity 110 mayautomatically generate an electronic acknowledgement that issent/transmitted to the IoT computing entity 130. In one exampleembodiment, the acknowledgement may be a signal to trigger/cause a lightof the button 215 of the IoT computing entity 130 to flash/blink (e.g.,flash periodically). In another example embodiment, the acknowledgementmay include data confirming the scheduling of pickup of one or moreitems at a location of the user and may include content specifying anestimated time for the pickup of the one or more items at the locationof the user.

As such, in one example embodiment, in response to the processor 200 ofthe IoT computing entity 130 detecting the electronic acknowledgement,the processor 205 (or message module 260) may cause/trigger a light ofthe button 215 to flash/blink (e.g., flash periodically during apredetermined time period (e.g., 15 seconds, 20 seconds, etc.)). Theflashing/blinking of the light of the button 215 denotes confirmation tothe user of the IoT computing entity 130 that the management computingentity 110 is arranging pickup of one or more items at a location of theuser in response to receipt of the signal(s)/message(s) from theprocessor 200 of the IoT computing entity 130 requesting pickup of oneor more items at the location of the user.

In another example embodiment, in response to the processor 200 of theIoT computing entity 130 detecting the electronic acknowledgement, theprocessor 205 (or message module 260) may provide visible indicia to thedisplay device 295 visibly indicating confirmation that the managementcomputing entity 110 scheduled pickup of the one or more items at thelocation of the user of the IoT computing entity 130 and visiblyindicating an estimated time for pickup of the one or more items at thelocation of the user. In addition, the electronic acknowledgementreceived by the processor 200 of the IoT computing entity 130 from theprocessor 205 (or message module 260) of the management computing entity110 may automatically trigger the processor 200 to generate one or moreelectronic shipping labels for shipping and tracking of the one or moreitems. In this regard, the processor 200 of the IoT computing entity 130may communicate with and instruct the printer 297 to print the one ormore generated electronic shipping labels. In response to receipt of theinstruction(s) from the processor 200 of the IoT computing entity 130,the printer 297 may print the one or more generated electronic shippinglabels.

The management computing entity 110 may determine that the location ofthe user for pickup of the one or more items corresponds to an addressof the user indicated in the data of the profile of the user in responseto analyzing the profile stored in memory 263 or the storage device 268.In this regard, in an instance in which the location of the address(es)information denoted in the profile of the user is utilized by themanagement computing entity 110 as the location for pickup of the one ormore items at the location of the user, the IoT computing entity 130need not necessarily be present at the location. Alternatively oradditionally, the management computing entity 110 may determine thelocation of the user for pickup of one or more items corresponds to thegeolocation information (e.g., latitude and longitude coordinates)indicated in the signal(s)/electronic message(s) received from theprocessor 200 of the IoT computing entity 130. Moreover, in someexemplary embodiments, the profile of the user may specify whether toutilize the address(es) indicated in the profile or a geolocationindicated in the signal(s)/message(s) received from the processor 200 ofthe IoT computing entity 130 as the location for pickup of one or moreitems of the user.

The dispatch module 250 of the management computing entity 110 maydetermine an estimated time for pickup of the one or more items at thelocation of the user of the IoT computing entity 130 based in part onidentifying the geographic area (e.g., determined from location datareceived from the information/data collection device 132 and/ortelematics sensors 125, location sensors 120) associated with thelocation of the user and determining a particular travel route to thelocation of the user in the geographic area. The dispatch module 250 mayalso determine the estimated time for pickup of the one or more items atthe location of the user by analyzing a trace history (e.g., historicaldata pertaining to a specified order in which to deliver/pickup items ona route to a location) or delivery history (e.g., past delivery historyto the location or nearby locations, traffic congestion history in thegeographic area) to the location or other locations nearby in thegeographic area in order to estimate when an assigned driver of avehicle (e.g., vehicle 100) may arrive at the location of the user forpickup of one or more items. For example, by evaluating the tracehistory or delivery history, the dispatch module 250 may determine anaverage time it takes for a vehicle (e.g., vehicle 100) to arrive at alocation for pickup of one or more items. The determined average timemay be used by the dispatch module 250 as the estimated time for pickupof one or more items at the location of the user of the IoT computingentity 130.

In some exemplary embodiments, the dispatch module 250 of the managementcomputing entity 110 may be able to monitor vehicles in real-time anddetermine which vehicle(s), among a fleet of vehicles, is the closest(e.g., by receiving geo-coordinates from an information/data collectiondevice 132 and/or telematics sensor 125, location sensor 120 of thevehicles) to the location of the user of the IoT computing entity 130and may determine an estimated time for the determined closest vehicleto divert from its current travel route and arrive at the location ofthe user of the IoT computing entity 130, via another travel route, forpickup of one or more items.

In an exemplary embodiment, as a vehicle (e.g., vehicle 100) travels andenters a predetermined distance (e.g., 3 miles, 5 miles, etc.) from thelocation of the user of the IoT computing entity 130, the processingdevice 408 of a mobile computing entity 105, and/or the dispatch module250 of the management computing entity 110, may send visible indicia tothe display device 295 of the IoT computing entity 130 visuallyindicating that the vehicle is within the predetermined distance (e.g.,3 miles, 5 miles, etc.) from the location and within an estimated timefor arriving at the location (e.g., within 10 minutes, 5 minutes, etc.).

In another example embodiment, in an instance in which the dispatchmodule 250 may determine that an assigned vehicle for arriving at thelocation is not on schedule to arrive (e.g., due to current trafficcongestion in the geographic area detected by real-time GPS data of theinformation/data collection device 132 and/or telematics sensor 125,location sensor 120, etc.) at the location of the user at the initialestimated time of arrival, the dispatch module 250 may recalculate(e.g., based on the trace history, the delivery history and the currentdetected traffic congestion) an estimated time of arrival. In thisregard, the dispatch module 250 may send visible indicia, indicating therecalculated estimated time of arrival to the display device 295 of theIoT computing entity 130 to visually display the recalculated estimatedtime of arrival at the location of the user of the IoT computing entity130.

In an exemplary embodiment, upon arrival at the location of the user ofthe IoT computing entity 130, the driver of the vehicle (e.g., vehicle100) may collect one or more printed electronic shipping label(s),printed by the printer 297, and one or more items for pickup and mayinclude the one or more items in one or more corresponding packages. Thedriver may also affix the printed electronic shipping label(s) onto theone or more packages and may load the packages on the vehicle, whichdelivers the one or more packages, along a travel path determined by thedispatch module 250, to a destination address indicated in the profileof the user stored in the memory 263 or the storage device 268 of themanagement computing entity 110.

In one embodiment, each electronic shipping label(s) on each package(s)may include and/or be associated with a unique tracking identifier, suchas an alphanumeric identifier. Such tracking identifiers may berepresented as text, barcodes, tags, character strings, Aztec Codes,MaxiCodes, information/data Matrices, Quick Response (QR) Codes,electronic representations, and/or the like. A unique trackingidentifier (e.g., 1Z123456789) may be used by the management computingentity 110 to identify and track packages as they move through acarrier's transportation network. For example, information/datacomprising a tracking identifier can be read, scanned, transmitted,and/or the like, for example, by a mobile computing entity 105, toprovide and/or identify/determine the location (e.g., geolocation) of apackage in transit. Such tracking identifiers may be included onelectronic shipping labels with the unique tracking identifier printedthereon (e.g., in human and/or machine readable form).

Furthermore, in some alternative exemplary embodiments, an IoT computingentity (e.g., IoT computing entity 130) may optionally include multiple(e.g., two, four, etc.) push buttons (e.g., push buttons 215) and eachof the push buttons may be associated with or tied to respectivedifferent destination addresses in corresponding different profiles ofthe user stored in a memory (e.g., memory 263 or storage device 268) ofthe IoT computing entity (e.g., IoT computing entity 130). In thismanner, by analyzing by the different profiles of the user stored on thememory of the management computing entity 110, the dispatch module 250of the management computing entity 110 may schedule and arrange forpickup of different sets of one or more items at the location of theuser of an IoT computing entity (e.g., IoT computing entity 130) fordelivery to different destinations in response receipt of respectivesignals/messages from the IoT computing entity in an instance in whichcorresponding different push buttons are depressed/selected.

Furthermore, in some other alternative exemplary embodiments, an IoTcomputing entity (e.g., IoT computing entity 130) may have multipledifferent colored push buttons (e.g., push buttons 215) and eachdifferent colored push button(s) (e.g., push buttons 215) may beassociated with a different type(s) of pickup service(s) (e.g., anext-day delivery service, a two-day delivery service, a ground deliveryservice, etc.) being requested by the IoT computing entity from themanagement computing entity 110.

Referring now to FIG. 6 , an example embodiment of a flowchart forproviding notification of one or more items for pickup at a location ofa user is provided according to an example embodiment. At operation 600,an apparatus (e.g., IoT computing entity 130) may automatically send agenerated electronic message to a network device (e.g., managementcomputing entity 110) requesting pickup of one or more items at alocation (e.g., an office, a home, a store, etc.) of a user of theapparatus in response to detecting pressing or selection of a button(e.g., button 215) on an exterior of the apparatus.

At operation 605, the apparatus (e.g., IoT computing entity 130) mayreceive an electronic acknowledgement message from the network device(e.g., management computing entity 110) denoting (i) confirmation thatthe network device received the generated electronic message requestingpickup of the one or more items at the location of the user and (ii)scheduled pickup of the items from the location of the user at anestimated time (e.g., at 4:00 PM).

At operation 610, the apparatus (e.g., IoT computing entity 130) maygenerate a visible indication (e.g., a blinking/flashing light of abutton (e.g., button 215), data presented to a display device (e.g.,display device 295) confirming receipt of the request for pickup of theone or more items) regarding the pickup of the one or more items inresponse to detecting receipt of the electronic acknowledgement messagefrom the network device (e.g., management computing entity 110).

In one example embodiment, the apparatus (e.g., IoT computing entity130) may generate the visible indication by causing a light of thebutton (e.g., button 215) to blink/flash periodically during apredetermined time period (e.g., 15 seconds, 20 seconds, etc.). Inanother exemplary embodiment, the apparatus (e.g., IoT computing entity130) may generate the visible indication by presenting display ofvisible indicia, via a display device (e.g., display device 295) of theapparatus, indicating the confirmation that the network device (e.g.,management computing entity 110) received the message requesting pickupof the items at the location and indicating the estimated time of thepickup of the one more items at the location.

It should be pointed out that FIG. 6 is a flowchart of a system, methodand computer program product according to an example embodiment of theinvention. It will be understood that each block of the flowchart, andcombinations of blocks in the flowchart, can be implemented by variousmeans, such as hardware, firmware, and/or a computer program productincluding one or more computer program instructions.

IV. Conclusion

Many modifications and other embodiments of the inventions set forthherein will come to mind to one skilled in the art to which theseinventions pertain having the benefit of the teachings presented in theforegoing descriptions and the associated drawings. Therefore, it is tobe understood that the inventions are not to be limited to the specificembodiments disclosed and that modifications and other embodiments areintended to be included within the scope of the appended claims.Although specific terms are employed herein, they are used in a genericand descriptive sense only and not for purposes of limitation.

That which is claimed:
 1. A method comprising: receiving, by one or morecomputer processors from an Internet of Things (IoT) device, anelectronic message requesting pickup of an item for shipping, whereinthe IoT device is associated with a profile; and responsive to receivingthe electronic message: determining, by the one or more computerprocessors from the profile, a location for pickup of the item;identifying, by the one or more computer processors and based at leastin part on the location, a geographic area that a delivery vehicle is totravel; determining, by the one or more computer processors and based atleast in part on the geographic area, a travel route to the location;determining, by the one or more computer processors and based at leastin part on the travel route, an estimated time for picking up the itemfrom the location; transmitting, by the one or more computer processors,an electronic acknowledgement message to the IoT device, wherein theelectronic acknowledge message is configured to cause the IoT device tovisually display the estimated time; and causing, by the one or morecomputer processors, the delivery vehicle to divert from a currenttravel route so that the delivery vehicle arrives at the location. 2.The method of claim 1 further comprising identifying, by the one or morecomputer processors based at least in part on geo-coordinates providedby a fleet of delivery vehicles operating in the geographic area, thatthe delivery vehicle is closest to the location from the fleet ofdelivery vehicles.
 3. The method of claim 1 further comprising, uponsending the electronic acknowledgement message: determining, by the oneor more computer processors based at least in part on geo-coordinatesprovided by the delivery vehicle, that the delivery vehicle is not onschedule to arrive at the location by the estimated time; and responsiveto determining the delivery vehicle is not on schedule to arrive at thelocation by the estimated time: determining, by the one or more computerprocessors, a revised estimated time for picking up the item from thelocation; and transmitting, by the one or more computer processors, anelectronic revision message to the IoT device, wherein the electronicrevision message is configured to cause the IoT device to visuallydisplay the revised estimated time.
 4. The method of claim 1 furthercomprising: determining, by the one or more computer processors based atleast in part on geo-coordinates provided by the delivery vehicle, thatthe delivery vehicle has entered a predetermined distance from thelocation; and responsive to determining the delivery vehicle as enteredthe predetermined distance from the location, transmitting, by the oneor more computer processors, an electronic update message to the IoTdevice, wherein the electronic update message is configured to cause theIoT device to visually display an indication that the delivery vehiclehas entered the predetermined distance from the location.
 5. The methodof claim 1, wherein the electronic acknowledge message is configured tocause the IoT device to have an electronic shipping label printed to usein shipping the item.
 6. The method of claim 1, wherein the electronicmessage requesting pickup comprises a geolocation of the IoT device, andthe method further comprises: determining, by the one or more computerprocessors, that a location identified in the profile is different thanthe geolocation; and determining, by the one or more computer processorsand based on the profile, to use the location in the profile as thelocation for pickup of the item.
 7. The method of claim 1, wherein theelectronic message requesting pickup comprises a geolocation of the IoTdevice, and the method further comprises: determining, by the one ormore computer processors, that a location identified in the profile isdifferent than the geolocation; and determining, by the one or morecomputer processors and based on the profile, to use the location in thegeolocation as the location for pickup of the item.
 8. A systemcomprising: a non-transitory computer-readable medium storinginstructions; and processing hardware communicatively coupled to thenon-transitory computer-readable medium, wherein the processing hardwareis configured to execute the instructions and thereby perform operationscomprising: receiving, from an Internet of Things (IoT) device, anelectronic message requesting pickup of an item for shipping, whereinthe IoT device is associated with a profile; and responsive to receivingthe electronic message: determining, from the profile, a location forpickup of the item; identifying, based at least in part on the location,a geographic area that a delivery vehicle is to travel; analyzing atrace history for the geographic area, wherein the trace historycomprises historical data on at least one specific order involvingdelivering or picking up an item on a travel route involving thelocation or another location nearby the location in the geographic area;determining, based at least in part on analyzing the trace history, anestimated time for picking up the item from the location; transmittingan electronic acknowledgement message to the IoT device, wherein theelectronic acknowledge message is configured to cause the IoT device tovisually display the estimated time; and causing the delivery vehicle todivert from a current travel route so that the delivery vehicle arrivesat the location.
 9. The system of claim 8, wherein the operationsfurther comprise identifying, based at least in part on geo-coordinatesprovided by a fleet of delivery vehicles operating in the geographicarea, that the delivery vehicle is closest to the location from thefleet of delivery vehicles.
 10. The system of claim 8, wherein theoperations further comprise: determining, based at least in part ongeo-coordinates provided by the delivery vehicle, that the deliveryvehicle is not on schedule to arrive at the location by the estimatedtime; and responsive to determining the delivery vehicle is not onschedule to arrive at the location by the estimated time: determining arevised estimated time for picking up the item from the location; andtransmitting an electronic revision message to the IoT device, whereinthe electronic revision message is configured to cause the IoT device tovisually display the revised estimated time.
 11. The system of claim 8,wherein the operations further comprise: determining, based at least inpart on geo-coordinates provided by the delivery vehicle, that thedelivery vehicle has entered a predetermined distance from the location;and responsive to determining the delivery vehicle as entered thepredetermined distance from the location, transmitting an electronicupdate message to the IoT device, wherein the electronic update messageis configured to cause the IoT device to visually display an indicationthat the delivery vehicle has entered the predetermined distance fromthe location.
 12. The system of claim 8, wherein the electronicacknowledge message is configured to cause the IoT device to have anelectronic shipping label printed to use in shipping the item.
 13. Thesystem of claim 8, wherein the electronic message requesting pickupcomprises a geolocation of the IoT device, and the operations furthercomprise: determining that a location identified in the profile isdifferent than the geolocation; and determining, based on the profile,to use the location in the profile as the location for pickup of theitem.
 14. The system of claim 8, wherein the electronic messagerequesting pickup comprises a geolocation of the IoT device, and theoperations further comprise: determining that a location identified inthe profile is different than the geolocation; and determining, based onthe profile, to use the location in the geolocation as the location forpickup of the item.
 15. A non-transitory computer-readable mediumstoring computer-executable instructions that, when executed byprocessing hardware, configure the processing hardware to performoperations comprising: receiving, from an Internet of Things (IoT)device, an electronic message requesting pickup of an item for shipping,wherein the IoT device is associated with a profile; and responsive toreceiving the electronic message: determining, from the profile, alocation for pickup of the item; identifying, based at least in part onthe location, a geographic area that a delivery vehicle is to travel;determining, based at least in part on the geographic area, a travelroute to the location; determining, based at least in part on the travelroute, an estimated time for picking up the item from the location; andtransmitting an electronic acknowledgement message to the IoT device,wherein the electronic acknowledge message is configured to cause theIoT device to visually display the estimated time.
 16. Thenon-transitory computer-readable medium of claim 15, wherein theoperations further comprise identifying, based at least in part ongeo-coordinates provided by a fleet of delivery vehicles operating inthe geographic area, that the delivery vehicle is closest to thelocation from the fleet of delivery vehicles.
 17. The non-transitorycomputer-readable medium of claim 15, wherein the operations furthercomprise: determining, based at least in part on geo-coordinatesprovided by the delivery vehicle, that the delivery vehicle is not onschedule to arrive at the location by the estimated time; and responsiveto determining the delivery vehicle is not on schedule to arrive at thelocation by the estimated time: determining a revised estimated time forpicking up the item from the location; and transmitting an electronicrevision message to the IoT device, wherein the electronic revisionmessage is configured to cause the IoT device to visually display therevised estimated time.
 8. The non-transitory computer-readable mediumof claim 15, wherein the operations further comprise: determining, basedat least in part on geo-coordinates provided by the delivery vehicle,that the delivery vehicle has entered a predetermined distance from thelocation; and responsive to determining the delivery vehicle as enteredthe predetermined distance from the location, transmitting an electronicupdate message to the IoT device, wherein the electronic update messageis configured to cause the IoT device to visually display an indicationthat the delivery vehicle has entered the predetermined distance fromthe location.
 19. The non-transitory computer-readable medium of claim15, wherein the electronic message requesting pickup comprises ageolocation of the IoT device, and the operations further comprise:determining that a location identified in the profile is different thanthe geolocation; and determining, based on the profile, to use thelocation in the profile as the location for pickup of the item.
 20. Thenon-transitory computer-readable medium of claim 15, wherein theelectronic message requesting pickup comprises a geolocation of the IoTdevice, and the operations further comprise: determining that a locationidentified in the profile is different than the geolocation; anddetermining, based on the profile, to use the location in thegeolocation as the location for pickup of the item.